Object-oriented editor for creating world wide web documents

ABSTRACT

An object-oriented HTML based editor for creating Web documents to be published on the World Wide Web. Each HTML command is treated as a unique object having associated properties. A user using an input device, such as a mouse, clicks and drags representations of objects representing HTML commands from a palette window on an output display device. The objects are dropped into a representation of a collection of objects in a view window on the output display device. Each one of the objects in the collection of objects may be edited by way of a context sensitive object editor window to customize the Web document. An object is selected by an input device and dragged to the object editor window, where the properties associated with the object are displayed and may be directly manipulated.

FIELD OF THE INVENTION

The present invention relates to a computer mediated method andapparatus for editing and publishing a Web document, or Web "page" onthe Internet's World Wide Web.

BACKGROUND OF THE INVENTION

The World Wide Web (the "Web") is a graphical hypertext-based interfacethat enables users to quickly move between Web sites and Web documents,also known as Web pages, on the Internet by following links to other Webdocuments or Web sites (Web pages) embedded within a Web document (Webpage).

Creating a Web Document

A Web document may contain many forms of information, including text,graphics, video, audio, and links to other Web documents anywhere in theworld. Presently, Hypertext Mark-up Language (HTML) is the standardformat for documents on the World Wide Web. An HTML formatted documenthas HTML codes, i.e., commands, embedded in the document.

A software application known as a Web browser is used to accessdocuments on the Web. By understanding HTML, Web browser software canproperly display a Web document on a user's output display device. Moreimportantly, Web browser software interprets the HTML commands in anHTML formatted Web document to navigate a link in that Web document toanother Web document. The Web browser thereby provides automatic accessto other Web documents on the Web.

A user with an understanding of HTML can create an HTML formatted Webdocument using any text editor software application, e.g., SimpleText,available from Apple Computer, Inc. SimpleText is a basic AmericanStandard Code for Information Interchange (ASCII) text editorapplication. However, the user has to embed HTML "tags" in the Webdocument.

HTML tags are inserted at the appropriate locations in a Web document toinform a Web browser how to display the various kinds of information inthe Web document. For example, FIG. 2 illustrates an HTML formatteddocument 200. The document is interpreted and displayed on a user'soutput display device using a Web browser such as Netscape Navigator',available from Netscape Communications, Inc. FIG. 3 shows the display300 of the HTML document in FIG. 2 on an Apple Macintosh' computersystem using Netscape Navigator' Web browser software.

HTML tags are typically paired. For example, the pair of tags "<html>"and "</html>" on lines 1 and 9 of FIG. 1 identifies the informationcontained between the tags as an HTML document. The HTML document iscomprised of a header indicated by the pair of tags "<head>" and"</head>" on lines 1 and 2, and a body indicated by the pair of tags"<body>" and "</body>" on lines 2 and 8, respectively.

The pair of "<h1>" and "</h1>" on line 3 indicates a heading. Headingsare numbered one through six, in order of decreasing font size. The texton line 4 ends with the end of paragraph tag "<P>". Upon detecting theend of a paragraph, a Web browser inserts a carriage return and alinefeed.

A horizontal rule tag, "<HR>", appears on line 5 of the HTML document. AWeb browser inserts a horizontal line across the output display deviceupon encountering this tag. As can be seen from the example HTMLdocument in FIG. 1, editing a very simple Web document using a plaineditor requires an understanding of HTML and careful attention tosyntax.

Tag-based editors, also known as HTML editors, were developed to provideHTML extensions. The HTML extensions allow a user to edit a document,select a segment of the document and choose an appropriate HTML tag froma pull down menu or the like to insert the HTML tags around the selectedsegment of the document. This obviates the need for a user to learn thespecific keystroke sequences representing a given pair of HTML tags.However, there is still a significant difference between what the usersees in an HTML document such as illustrated in FIG. 1, and thecorresponding display illustrated in FIG. 2. Thus, a certain level ofuser-sophistication and trial and error is required to generate a Webdocument as desired by the user. To that end, more recent HTML editorsknown as What You See Is What You Get (WYSIWYG) editors have beenemployed to generate Web documents.

WYSIWYG HTML editors, such as WebMagic, available from Silicon Graphics,Incorporated, FrontPage, available from Vermeer Technologies,Incorporated, and Adobe PageMill, available from Adobe Systems,Incorporated, simplify the task of creating a Web page by presenting theuser's working page, i.e., a Web page being created by the user, as itwould appear when accessed by a Web browser. In constructing the page,changes can be made by simple direct manipulation, as in a traditionalword processor software application such as MacWrite, available fromClaris Corp. WYSIWYG editors remove the need for users to correctlyformulate the syntax and structure of a Web document and allow greaterattention to be paid to the visual appeal and format of the final Webdocument.

WYSIWYG editors are quite limited, however, by several structuralfeatures of HTML and the Web. One limitation is that the range of Webbrowsers and platforms is as variable as the range of all computers,meaning that the visual presentation provided by a WYSIWYG editor willbe appropriate for only a subset of the possible audiences of thedocument. A second limitation is that HTML is a rapidly evolvinglanguage with new features appearing every month, requiring expensiverewrites of WYSIWYG editors when major new features such as tables orframes appear. A third limitation is that WYSIWYG editors do nothing toexpose the underlying programmatic structure of an HTML document. Forthese reasons, many intermediate and nearly all expert users of HTMLproduce their documents "in the raw" without using a WYSIWYG editor.Thus, what is needed is a method for creating Web documents that removesthe need to understand HTML syntax while allowing the user to easilydiscern the format of the Web document as displayed on an output displaydevice.

Publishing a Web Document

With reference to FIG. 8, a simplified model of the elements comprisingthe World Wide Web (the "Web") on the Internet is depicted. The Web 810is a graphical, hypertext-based interface that overlays the Internet.The Internet is a collection of interconnected, autonomous datacommunication networks which spans the globe. A user at a computersystem executing a Web browser software application such as NetscapeNavigator can access information in the form of Web documents or pageson the Web. The information may reside on the same or different computersystem or systems. This model is often referred to as a client-servercomputing model, in which one or more clients 810 and 820 access orquery a server 830 over a data communications network.

A server on the Web serves, or publishes, Web documents over the Web.The documents are available to a user who accesses the server from aclient executing Web browser application software. The server and clientcommunicate using a communications protocol. Typically, a server andclient communicate over a data communications network underlying the Webusing an International Standards Organization (ISO) Open SystemsInterconnection (OSI) Application-layer protocol such as HyperTextTransfer Protocol (HTTP). The Application-layer protocol provides amethod of communicating ASCII-based, HTML-formatted informationcomprising a Web document published by a server. The Web document istransmitted over a data communications network to a client upon requestfrom the client. The HTTP protocol, as an Application-layer protocol,utilizes the services of a standard set of OSI Transport-layer andNetwork-layer data communication protocols such as the Transport ControlProtocol/Internet Protocol (TCP/IP) suite of data communicationprotocols.

A client on the Web is comprised of a computer system executing Webbrowser application software. The client communicates with the serverusing HTTP, but must understand HTML as well, so that, among otherthings, upon receiving an HTML document from the server, the clientknows how to display the document on an attached output display device.

As described above, HTML documents have traditionally been plain ASCIItext files with HTML tags inserted at appropriate locations within thetext file. The files are stored in a file system, as depicted in FIG. 9.FIG. 9 illustrates a traditional hierarchical file system 900 having ahierarchical directory structure 901 by which files, e.g., file A (902),are organized on a permanent storage medium such as a magnetic disk.File C 903 is a subdirectory containing files X, Y and Z. File Z 905 isa subdirectory as well for files 1, 2 and 3.

A server running the HTTP, i.e., an HTTP server, receives a request froma client for a particular HTML document. The HTTP server scans its filesystem directory 901 in search of the data file or files storing theHTML document. Upon locating the file or files in the file system, theHTTP server transmits the contents of the file using the HTTP. Thus, theHTTP server has no knowledge, and in fact, needs no knowledge, of thecontent or format of the HTML document to publish, i.e., transmit, theHTML document to the client over the data communications network.

A disadvantage in the above approach is that the contents of the HTMLdocument are static. In other words, the contents of the HTML documentdo not change once created by an editor until such time as the documentis directly modified by a user via an editor. To overcome thislimitation, Common Gateway Interface Binary (CGI-bin) scripts weredeveloped, which are essentially per, C or C++ computer programs thatoutput HTML-formatted ASCII text at run time. CGI-bin scripts allowed aserver to generate content within an HTML document "on the fly," i.e.,dynamically, depending upon the current state of the server, e.g., thedate or time of day, or input from a user. The information provided asinput from a user could be information obtained from a client through anHTTP request, e.g., information regarding who or where the user islocated, security or access control information, etc.

As opposed to HTML documents, HTTP servers do need to understand aCGI-bin script insofar as a server must know where the scripts arelocated, how to execute the scripts, and how to receive the informationoutput by the script and convert the information, if necessary, to HTMLformat before transmitting it to a client over the data communicationsnetwork.

One disadvantage of CGI-bin scripts is the level of user sophisticationrequired to develop the scripts due to the computer program-like natureof the script language. Moreover, the scripts must be compiled, and arealso limited in that they output ASCII text which must then be convertedby the HTTP server or some other process to the appropriate format for aWeb document, e.g., HTML format. Additionally, the scripts are createdindependent of each other, making it difficult and time-consuming toestablish links between different CGI-bins scripts. What is needed is anobject oriented-based authoring and serving environment whereineverything is treated as an object and an object can send messages toother objects or alter the serving environment itself. Finally, scriptscannot be easily extended and specialized like objects can. What isneeded is a way for a user to take a certain object and create aspecialized subclass that worked in exactly the same manner except for adifferent feature depending on the conditions.

SUMMARY OF THE INVENTION

The present invention provides an object-oriented HTML based editor forcreating Web documents to be published on the World Wide Web. Each HTMLcommand is treated as a unique object having associated properties. Auser using an input device, such as a mouse, clicks and drags objectsrepresenting HTML commands from a palette window on an output displaydevice. The objects are dropped into a collection of objects in a viewwindow on the output display device. Each one of the objects in thecollection of objects may be edited by way of a context sensitive objecteditor to customize the Web document. An object is selected by an inputdevice and dragged to an object editor window, where the propertiesassociated with the object are displayed and may be modified.

The present invention allows the Web page created by the object-orientedHTML based editor to be saved as an object rather than a data file in afile system. The object can then be published by a server on the Web asis, or the object can output its contents in a format requested by aclient on the Web, e.g., an HTML formatted document.

It is a further object of the invention to provide a method forpublishing a Web document having dynamic information, such that eachtime the Web document is published, the information is up-to-date. Ascript language allows a user to create or edit an output handlerassociated with an object to provide dynamic behavior.

The aforementioned and further objects, features and advantages of thepresent invention will be apparent from the description and figureswhich follow.

BRIEF DESCRIPTION OF THE DRAWINGS

The present invention is illustrated by way of example and notlimitation in the following figures:

FIG. 1 illustrates a computer architecture upon which an embodiment ofthe present invention can be implemented.

FIG. 2 is an example of an HTML-formatted Web document created using aplain text editor software application.

FIG. 3 illustrates a display of a Web document corresponding to theexample Web document in FIG. 1.

FIG. 4 illustrates a message box window as may be utilized by anembodiment of the present invention.

FIG. 5A illustrates a palette window as may be utilized by an embodimentof the present invention.

FIG. 5B illustrates a palette window as may be utilized by an embodimentof the present invention.

FIG. 6A illustrates a Web page viewer window as may be utilized by anembodiment of the present invention.

FIG. 6B illustrates a Web page viewer window as may be utilized by anembodiment of the present invention.

FIG. 6C illustrates an object editor window as may be utilized by anembodiment of the present invention.

FIG. 6D illustrates an object editor window as may be utilized by anembodiment of the present invention.

FIG. 6E illustrates an object editor window as may be utilized by anembodiment of the present invention.

FIG. 7A illustrates a method for creating a user defined HTML object asmay be utilized by an embodiment of the present invention.

FIG. 7B illustrates a method for creating a user defined HTML object asmay be utilized by an embodiment of the present invention.

FIG. 8 illustrates a simplified model of the Internet's World Wide Web.

FIG. 9 illustrates the file system for a computer system as may beutilized by an embodiment of the present invention.

FIG. 10 is a diagram of an object system in which data objects arestored by an object oriented editor as may be embodied by the presentinvention.

FIG. 11 is a flowchart of a method for publishing a Web document on theWorld Wide Web as may be embodied by the present invention.

DETAILED DESCRIPTION OF THE PRESENT INVENTION

Introduction

The present invention provides an object-oriented HTML based editor forcreating Web documents to be published on the World Wide Web (the"Web"). The present invention further provides a method by which the Webdocuments created by the object-oriented HTML based editor are publishedon the Web. In the following description, numerous specific details areset forth describing specific representations of data, specificprocessing steps, etc., in order to provide a thorough understanding ofthe present invention. However, it will be apparent to one of ordinaryskill in the art to which the present invention pertains, or with whichit is most nearly connected, that the present invention may be practicedwithout the specific details disclosed herein. In other instances, wellknown systems or processes have not been shown in detail in order not tounnecessarily obscure the present invention.

The present description includes material protected by copyrights, suchas illustrations of graphical user interface images or text which theassignee of the present invention owns. The assignee hereby reserves itsrights, including copyright, in these materials, and each such materialshould be regarded as bearing the following notice: Copyright AppleComputer, Inc. The copyright owner has no objection to the facsimilereproduction by anyone of the patent document or the patent disclosure,as it appears in the Patent and Trademark Office file or records, butotherwise reserves all copyrights whatsoever.

Computer Hardware

Referring to FIG. 1, the computer system upon which the preferredembodiment of the present invention can be implemented is shown as 100.Computer system 100 comprises a bus or other communication means 101 forcommunicating information, and a processing means 102 coupled with bus101 for processing information. System 100 further comprises a randomaccess memory (RAM) or other dynamic storage device 104 (referred to asmain memory), coupled to bus 101 for storing information andinstructions to be executed by processor 102. Main memory 104 also maybe used for storing temporary variables or other intermediateinformation during execution of instructions by processor 102. Computersystem 100 also comprises a read only memory (ROM) and/or other staticstorage device 106 coupled to bus 101 for storing static information andinstructions for processor 102. Data storage device 107 is coupled tobus 101 for storing information and instructions.

A data storage device 107 such as a magnetic disk or optical disk andits corresponding disk drive can be coupled to computer system 100.Computer system 100 can also be coupled via bus 101 to an output displaydevice 121, such as a cathode ray tube (CRT), for displaying informationto a computer user. An alphanumeric input device 122, includingalphanumeric and other keys, is typically coupled to bus 101 forcommunicating information and command selections to processor 102.Another type of user input device is cursor control 123, such as amouse, a trackball, or cursor direction keys for communicating directioninformation and command selections to processor 102 and for controllingcursor movement on display 121. This input device typically has twodegrees of freedom in two axes, a first axis (e.g., x) and a second axis(e.g., y), which allows the device to specify positions in a plane.

Alternatively, other input devices such as a stylus or pen can be usedto interact with the display. A displayed object on a computer screencan be selected by using a stylus or pen to touch the displayed object.The computer detects the selection by implementing a touch sensitivescreen. Similarly, a light pen and a light sensitive screen can be usedfor selecting a displayed object. Such devices may thus detect selectionposition and the selection as a single operation instead of the "pointand click," as in a system incorporating a mouse or trackball. Stylusand pen based input devices as well as touch and light sensitive screensare well known in the art. Such a system may also lack a keyboard suchas 122 wherein all interface is provided via the stylus as a writinginstrument (like a pen) and the written text is interpreted usingoptical character recognition (OCR) techniques.

Finally, in the currently preferred embodiment of the invention,computer system 100 is configured with a network interface card forcoupling computer system 100 to a data communications network.

Object Oriented Editor

An embodiment of the present invention providing for an object orientedauthoring environment for creating Web documents will now be described.The environment is comprised of an object system, object framework,script language, and a user interface.

Object System

The object system represents all data and procedures as objects. Acharacter, for example, is a character object. An integer is an integerobject. A project, e.g., a Web document, is an object. Each object hasan associated set of properties and handlers. A property is storagespace in an object. The storage has a name and holds exactly one value.In general, properties in an object oriented system are known asinstance variables. A handler is a named segment of software code thatis executed in response to a message, e.g., in response to an objectinforming another object to perform a function.

The object system is based on a prototype-based model where every objectcan be a template for creating new objects with different types ofproperties and handlers. In a prototype-based model, no distinction ismade between an object and a template, i.e., all objects can betemplates for other objects. In a prototype-based model, every object isa prototype, and every prototype is a type. Thus, each object is a type.The type represents the values of the properties and handler behaviorassociated with the object. Type is determined by inheritance from oneor more parent objects. An object can refer to other objects. A propertyis an object reference. Objects can include other objects by reference.In fact, a property can include different types of objects at differenttimes.

The object system provides support for many object, handler, andproperty related functions, including, but not limited to, adding orremoving a property associated with an object, creating a child of anobject, and duplicating an object.

Objects and their associated or inherited properties and handlers areorganized into an object inheritance heterarchy where each object is thechild of some other object. The structure is a heterarchy rather than ahierarchy due to the fact that an object can have more than one parent.The top object of the heterarchy is the object Object. Object containsall the handlers needed to create new objects or copies of objects,initialize objects, add or remove properties, assign object names, etc.

The object inheritance heterarchy lends itself well to HTML formattedWeb documents which naturally have a hierarchical containment structureto them (e.g., an HTML document contains a head and a body, a bodycontains tables, headers, lists and paragraphs, a list contains listheadings and list items, etc.) This property of containment is usedheavily by the object oriented editor of the present invention,especially for the creation of custom objects created by the user.

The present invention also provides for the creation of a hierarchy ofHTML objects which contain methods to 1) create appropriate HTML, 2)provide for an extensible and flexible list of attributes, and 3) createon-screen editor features. Additionally, the present invention providesfor overriding any of these methods for any given object(s). Thecreation of a flexible and extensible list of attributes is useful sothat if the protocol for HTML changes in the future (e.g., if futureversions of HTML provide for horizontal rules to have an associatedcolor), the user could easily make the required changes to the objectoriented editor of the present invention without any need for arecompilation or redistribution of an HTML document by the developer.This also provides a user with the ability to take out unwanted featuresin an HTML document.

Concept of Objects, Properties, and Handlers

Objects are analogous to nouns in the English language. An object is athing. Objects are defined in terms of other objects. An object isdefined by the object's features and the object's relationship to itsparents. The features of an object are its properties and handlers. Anobject can be a child of one or more parents. A child inherits thefeatures of its parent(s). Since a parent object inherits the featuresof its parents, the child inherits the features of its ancestors.

An example of an object is the HTML horizontal rule (HR). The object HRcan be used to store information about horizontals rules in a Webdocument. Thus, the object HR has properties associated with it such aswidth, size, alignment, and shading. Each of these properties, in turn,can have a value, e.g., width=100%, alignment=center, etc. The object HRcan be enriched by defining a handler for it that makes some use of theinformation associated with the object.

Properties are analogous to adjectives in the English language. Aproperty is storage space in an object. This storage has a name and canhold exactly one value. This value can be anything ranging from aBoolean value to a collection of values including a list, an array, orany kind of object.

Handlers are similar to verbs in the English language. The behavior ofand operations performed on objects are controlled by handlers. Amessage handler, or simply, handler, is a named piece of software codethat is executed in response to a message or event. Handlers areprocedures available to an object that specify some action to beperformed. A handle is the name of a behavior that the object is askedto perform.

Object Framework

The Object Framework provides a set of objects for developing Webdocuments. The framework provides objects that represent files,Input/Output (I/O) devices, sounds, shapes, dates, clocks, etc., i.e.,objects that abstract away particulars of a computer operating systemand hardware upon which the Web document is created and published. Inaddition, objects are provided for low level graphics and much higherlevel aspects of graphics, including objects for traditional data typessuch as integers, characters, strings, as well as arbitrary collectionsof objects, arrays, list and vectors, objects that handle errors andevents, and user interface objects such as buttons and scrollers.

Script Language

A script language is provided by an embodiment of the present invention.The script language is a complete object oriented programming languagefor writing, compiling, and executing handlers, obviating the need todevelop the handlers in lower-level code. Because the script language isan object oriented language, script code is associated with an object.Such code is called a `functional-handler`, or simply, handler. Eachhandler is owned by exactly one object. New objects are created fromexisting objects. By default, a new object shares, or `inherits` all thehandlers owned or inherited by the objects it is created from, i.e., theobject's parents.

User Interface

A user interface, termed Project Builder, provides for general purposedirect manipulation of a user project, e.g., for developing a Webdocument. The Project Builder provides a variety of object and scriptlanguage browsers and editors. A user project is the workspace in whicha user develops a Web document. The process of building a Web documentconsists of the general steps of designing a user interface for the Webdocument, customizing the interface by changing properties and scriptingthe interface to provide a certain behavior, experimenting with the lookand feel of the interface, and finally, continuing with a more detailedimplementation of the Web document's functional requirements.

User Interface Windows

In one embodiment of the present invention, The Project Builderinterface has windows that are characterized by an appearance similar indesign to the Apple Macintosh computer system, but distinct enough toavoid confusion with the Web document a user is creating.

In many of the windows, there are multiple panels in which a user cantype. The field which is highlighted in white is the active typingfield. If the window is not selected, all panels therein are gray. Whenthe window is active, one of the panels is white to indicate that anykeystrokes will be sent to this panel. Within any window, the Tab keychanges focus from one panel to another panel.

The Project Builder interface supports drag and drop operations. A usercan use an input device such as a mouse to click on, then drag and dropreferences to objects, properties, and handlers between the variouswindows, editors and browsers. For example, as will be described withreference to a specific example below, a user can click on a particularobject for a period of time, such as half of a second, and a gray boxappears around the name of the object. The box can be dragged to a fieldin an editor or window and dropped there to cause the editor or windowto focus on this object. Indeed, several objects can be selected,dragged and dropped in this manner, for example, by simultaneouslyholding down the shift key on a keyboard while clicking on the objectswith an input device such as a mouse. It should be noted that the useris not dragging the actual objects around, only references to theobjects. Dragging a reference around will not affect the object.

Throughout Project Builder, an item can be selected and the delete keypressed to remove it. For example, a user can select a handler and pressthe delete key to remove the handler. In the same manner, the user candelete properties, handlers, functions, constants and variables. Objectscan be removed in the same way, provided there is not a reference to theobject.

Many of the Project Builder windows are designed to provide a user withcontext sensitive information. A description of the various windows thatappear on output display device 121 follows.

Message Box Window

With reference to FIG. 4, the Message Box window 400 provides a windowin which to type script commands and receive system messages. TheMessage Box window 400 is comprised of a listener panel 401, panelsplitter 402 and display panel 403. The listener panel 401 is a scriptcommand line interface that allows a user to communicate with theProject Builder interface by typing into it. When the Return or Enterkey is pressed, the listener panel 401 evaluates the script commandtyped therein and responds in the display panel 403. Panel splitter 402separates listener panel 401 from display panel 403.

Display panel 403 displays messages from the object oriented editor ofthe present invention. The display panel 403 provides responses tocommands entered into the listener panel 401. Display panel 403 alsoprovides status information during the execution of certain operations,such as saving or loading a Web document.

HTML Palette Window

FIGS. 5A and 5B illustrate the HTML Palette window 500. The HTML Palettewindow 500 has two panels: user panel 501, and widgets panel 502, whichmay display different libraries of predefined HTML objects, such as thelibrary of HTML header objects illustrated in FIG. 5A, or the library ofHTML body objects illustrated in FIG. 5B. To select an object in eitherof the panels, a user clicks on the object. To switch between thelibrary of HTML header objects and the library of HTML body objects, auser pulls down on the pull down menu 503 at the top right corner of thewidgets panel 502.

The user panel 501, although illustrated as empty in FIGS. 5A and 5B,displays new user-defined HTML objects created by the user. It ispossible to drag and drop an HTML object from widgets panel 502 to userpanel 501. The user may first choose to modify a predefined HTML objectfrom widgets panel 502, rename it, and store it in user panel 501. Thepredefined HTML object is modified by the user first dragging the HTMLobject to an object editor window, as described in more detail below.This allows a user to reuse a predefined HTML object, such as a header,by modifying a property or handler associated with the predefined HTMLobject, and creating a new user-defined HTML object that is identical tothe predefined HTML object with the exception of the modified propertyor handler. This ability is fundamental to the concept of softwarereuseability in object oriented programming. The ability to click anddrag on a predefined object for the purpose of reusing the object tocreate custom objects provides for efficient construction of Webdocuments. For example, the object oriented editor of the presentinvention provides for the creation of a custom user object, such as anobject named EmployeeInfoObject, which comprises a table containing theobjects: employee name, picture, and employment date. Once the objectEmployeeInfoObject is created, a user can click on the object and dragit to the user palette where copies can be made for each employee,without regard for or an understanding of the structure of the object.

HTML Page Viewer Window

With reference to FIG. 6A, an embodiment of the present inventionprovides an HTML Page Viewer window 600 (the "viewer window") via whicha user can create and display a representation of a collection of HTMLobjects comprising a Web document (i.e., Web page). The Page Viewerwindow 600 is comprised of a title panel 601 and a page structure panel608. Title panel 601 displays at pull down menu 607 the title of thepage whose structure appears in page structure panel 608. A user can usean input device such as a mouse to pull down on pull down menu 607 toselect from a number of Web pages. A representation of the collection ofobjects comprising the Web page selected is then displayed in pagestructure panel 608 of the viewer window.

Save button 603 saves the current Web page into the user project.Preview button 604 previews the current Web page by sending aninterprocess communication signal to a concurrently running Web browser,e.g., Netscape Navigator, available from Netscape Communications. Whenpreviewing a Web page, the page is rendered into text, saved into atemporary file on a permanent storage medium and passed to a Web browserwith instructions to open the temporary file and display it in a windowon an output display device, for example, the same output display deviceon which the windows of the object editor of the present invention arebeing displayed. Indeed, a user often positions the Web browser windowalong side the object editor window, thereby allowing side-by-sideediting and previewing. By using separate Web browser applicationsoftware, the present invention allows the user to try out a Web pagewith any Web browser. Additionally, New button 605 creates a new Webpage, wherein the user is prompted for a Web page name. Finally, Deletebutton 605 deletes the current Web page.

Page structure panel 608 displays a representation of a collection ofobjects from different segments of a Web page depending on what menu isselected from pull down menu 609. Page structure panel 608 can display arepresentation of a collection of objects from a Web page headersegment, as illustrated in FIG. 6A, or a representation of a collectionof objects from a Web page body segment, as illustrated in FIG. 6B. Toswitch between the header segment display and the body segment displayin the page structure panel 608, a user pulls down on the pull down menu609 at the top right corner of the page structure panel 608.

Having selected either a header or body Web page segment for display inthe page structure panel 608, a user can create or modify an existingWeb page by clicking on, i.e., selecting, and dragging the appropriaterepresentation of HTML objects from the widgets panel 502 in the HTMLPalette window 500 to the page structured panel 608 and dropping therepresentation of HTML objects therein. For example, with reference toFIG. 6C, a user can click on and drag a representation of the HTMLobject Header (at 620) and drop the representation of the HTML objectHeader in the body segment display of page structure panel 608 (at 621).

A user can also remove an object from the collection of objectscomprising the Web page by using an input device to click on therepresentation of the object in the page structure panel 608 andpressing the delete key on the keyboard.

Object Editor Window

With reference to FIG. 6C, the Object Editor window 610 allows theviewing and modification of objects. It displays all aspects of anobject, including the properties associated with the object, propertyvalues, and handlers defined only by the object or its parent(s).Multiple Object Editor windows may be displayed on output display device121. Additionally, multiple objects and their associated properties maybe displayed in the Object Editor window at the same time, for example,by holding down the shift key on the keyboard while selecting objectswith an input device such as a mouse to drag and drop the objects intothe Object Editor window.

The Object Editor window, e.g., Object Editor window 610, is comprisedof a object display panel in which an icon 626 representing the objectand a corresponding name, e.g., HTMLText 623, representing the object,appears. Preview button 611 in the Object Editor window 610 demonstratesthe object oriented nature of the present invention. For example, sincea page, a paragraph, and a horizontal rule are all treated as objects,they share the same preview method. If, for example, a user is editing atable embedded in a complicated Web page, but wants to see just thetable and not all the other items around it, the user can select thetable and click on the Preview button 611 to preview just the table in aWeb browser window. This functionality is inherited from the root HTMLobject and provides preview functionality to every HTML object createdby the user.

The Object Editor window is further comprised of a properties displaypanel 614, via which a user is able to directly manipulate theproperties associated with the object. The Edit PostHTTP button 612 andEdit OutputHTML button 613 within properties display panel 614 areprovided for advanced users to write their own script methods on anyobject. A user can, for example, drag a horizontal rule into a documentand then make the horizontal rule appear as a graphical image. The userwould simply click on the rule, click on the Edit OutputHTML button andwrite a method that said something like, "if currentUser's fancyLayoutis TRUE then return "<img src=fancyrule.gif>" else return do inherited."(This assumes currentUser is a global variable that has been previouslyset up with some sort of object describing the user looking at the page;and, requires the scripter to understand HTML to the extent necessary tocreate the `img` tag). Because the horizontal rule object created in thefirst step is a new child of the root HorizontalRule object, the newbehavior attaches only to the child. If the user wants to use the objectagain, the user drags the object into the user objects panel 501 andreuses it. The outputHTML button 613 is a handler that is used when thecurrent Web page is requested by a remote user; a postHTTP handler canbe used when the user fills out a form and "posts" the form results tothe Web document (and therefore is useful for creating interactivepages).

Having selected an HTML object from either the user or widgets panel ofthe HTML Palette 500 for inclusion in the collection of objectscomprising the current Web document in the page structure panel, a usercan edit or modify the properties associated with the object via acontext sensitive object editor window. For example, with reference toFIG. 6C, a user clicks on the representation of the HTML object HTMLText622 in the page structure panel 608 of Viewer window 600. The user thendrags the representation of the HTML object HTMLText 622 and drops itinto Object Editor window 610. The object display panel shows an iconand an object name HTMLText 623 representing the HTML object.Furthermore, the properties display panel 614 provides access to thefont styles 625, information styles 626 and text string 624 propertiesassociated with the HTML object HTMLText. The user can manipulate any ofthese properties, as is illustrated by creating the text string "This isa header" in the property display panel.

As another example, with reference to FIG. 6D, a user clicks on arepresentation of the HTML object HTMLHorizRule 634 in the pagestructure panel 608. The user drags the representation and drops it intoObject Editor window 610. The object display panel provides an icon andobject name representing the HTML object HTMLHorizRule. The contextsensitive nature of the properties display panel is apparent whencomparing the properties display panel in FIG. 6C vis-a-vis theproperties display panel in FIG. 6D. The properties display panel 614 inthe latter case displays those properties associated with the HTMLobject HTMLHorizRule, namely, width 630, size 631, alignment 632 and theBoolean No Shading 633. FIG. 6E illustrates yet another example of thecontextual nature of the object editor window, in which the propertyLevel 640 is displayed in the properties display panel 614 for theassociated HTML object HTMLHeader, selected and dropped into the objecteditor window from the page structure panel 608. The property value is2, but may be modified to any value from one to six.

The concept of constrainment is illustrated by the pull down menus forthe properties font styles 623 and information styles 626 in FIG. 6C,and alignment 632 (e.g., center, left, and right) in FIG. 6D, and Level640 in FIG. 6E. A user is constrained as to the set of values from whichto choose for each property.

In an alternative embodiment, a property value for an object is editedby double-clicking on the property or selecting the property andpressing the Return or Enter key. The properties display panel isreplaced by a value editor panel for the particular property selected.

Additionally, a user can select an HTML object from either the user orwidgets panel of the HTML palette and drag the object directly to anobject editor window to directly manipulate the properties associatedwith the object via an object editor window.

With reference to FIG. 7A, an object whose properties have been modifiedmay be stored in user panel 501 of Palette window 500 for subsequent usein the collection of objects in a page opened in page structure panel608. Storing in the user panel an object whose properties have beenmodified can be accomplished a number of ways. The user can click anddrag a representation of an object, e.g., the representation 701 of HTMLobject Header from the page structure panel 608 to the user panel 501.If a property associated with the HTML object has been modified via theobject editor window so that the object no longer is identical to thepredefined object in the widgets panel 502, the user is prompted with apop up window 704. The user types in a new name for the modified object,e.g., BoldHeader (at 703), in the pop up window and presses the Returnor Enter key or selects the OK button. As illustrated in FIG. 7B, arepresentation of the modified object BoldHeader 703 then appears in theuser panel 501 of the Palette window 500.

Alternatively, a user can select the icon or name representing an objectin the object display panel of the object editor window and drag therepresentation to the user panel in the Palette window 500. As in thecase where the user selects the representation of the object from thepage structure panel, the user is prompted via a pop up window for aname for the object.

A direct manipulation editor for adding a property to a predefined HTMLobject is not provided. A property is added to an HTML object asfollows. Suppose the HTML protocol changed and images could have a"translucent" property. To add the property, the user types (at themessage box command line) syntax such as:

"insert {"translucent", "Is Translucent", checkbox} at end ofobjectPropertyList of HTMLImage"

The command adds a new entry with property name "translucent,"user-interface description "Is Translucent", and type "checkbox" (otheroptions include text, number, color, list, etc.) to the property listfor HTMLImage. The object editor of the present invention would thenreconfigure itself to display this new property, the outputHTML handlerwould correctly interpret it, and the parser would take note of it thenext time the user attempted to load a Web page.

A description for creating a dynamic object, e.g., a timestamp based onthe HTML object Header, follows. To create the dynamic object timestampbased on the HTML object Header, the user drags a new header into a pageand set its level to 2 (i.e., a reasonably large, bold header). Then theuser clicks on the "outputHTML" button in the object editor window forthe object Header. A script editor window appears, into which the usertypes:

global theDate

global theTime

return theTime as string & "," & theDate as string

The user then saves the changes and exits the script editor. To keep thenew object, the user clicks on it and drags it to the user panel 501. Anembodiment of the present invention then asks for a name, to which theuser responds, for example, by typing "TimeStampObject." A dynamic,reusable timestamp object is now placed in the list of widgets inwidgets panel 502. Note that while this is a fairly advanced example ofcreating a dynamic object, many useful compound objects can be createdwithout any scripting at all, simply by compositing a set of usefulobjects into a container, as set forth in the example of "employeeInfo"above.

Publishing a Web Document

An embodiment of the object oriented editor described above saves anHTML document as an object, rather than a data file. FIG. 10 illustratesobject oriented editor 1000 on a server 830 saving Web documents asobjects, such as object 1010. Recall from the above discussion that anobject is itself a collection of objects.

The object comprising a Web document can be transferred by the server toa client over a data communications network. Alternatively, the objectcomprising the Web document can be executed by the server. The object,in turn, causes each object contained therein to execute and output arepresentation of the object in whatever format is requested by theclient. For example, a client can send a request to the server over thedata communications network. The requests specifies a particular Webdocument. The server searches it collection of objects in its objectspace for the object requested. The server, upon finding the object, anddepending upon the nature of the client's request, will publish, i.e.,transmit, the object as is to the client, or execute the object. Theobject outputs a representation of each object contained within theobject in a format specified by the client. Thus, if the client requestsan HTML formatted Web document, the server executes the objectrepresenting the Web document, passing as input to the object, an inputargument indicating the output of each object within the Web document isto be formatted in HTML.

With reference to FIG. 11, a method of publishing a Web document asembodied by the present invention is more fully explained. The processbegins at step 1101 with the server and client having established anapplication-layer communication protocol connection. In the presentembodiment, the client and server communicate with each other over adata communications network using HTTP. It is understood, of course,that other application-layer protocols may be used to establish andmaintain appropriate communications between the client and server.

At step 1102, the server receives a request from a client over a datacommunications network. The request specifies an object, e.g., a Webdocument a user wants to display on the output display device coupled tothe client. The request may also specify a property or a list ofproperties. A value or list of values may be assigned to the property orlist or properties.

At step 1103, a handler for the root object Object searches in theobject space on the server for the object specified by the client. Atstep 1104, a message is returned depending on whether the objectspecified by the client is found. If the object is not found, thehandler, at step 1105, returns a message to the server that the objectis not found. The server, in turn, communicates the message via the HTTPto the client. If, however, the object is found, the handler determines,at step 1106, whether a read (get) from or write (post) to the object isto be performed. Generally, publishing a Web document involves a readfrom the object representing the Web document, and so the flow chartcontinues to step 1107.

At step 1107, the object checks for the presence of input arguments,e.g., properties and values assigned to the properties. If arguments arepresent,

At step 1108, the "outputHTML" handler of every object in the page iscalled in an pre-order traversal of the container hierarchy. If thereexists, for example, a header object containing an image object and atext object, the handler would perform the following steps:

    ______________________________________    outputHTML the header (insert "<H1>" into stream)    outputHTML the image (insert "<IMG attributes...>" into    stream)    finish outputHTML the image (no action)    outputHTML the text (insert "...the text..." into stream)    finish outputHTML the text (no action)    finish outputHTML the header (insert "</H1>" into stream)    ______________________________________

When the process completes, the stream contains the entire Web page. TheWeb page can be used in any manner. For example, the Web page could beto the network to answer a remote request, saved to a temporary file ondisk for use in a preview, or displayed to the user in a text buffer.

At step 1109, the handler outputs an HTML formatted representation ofthe object to the server. The last step, at 1110, is publishing, i.e.,transmitting, the HTML formatted output the client.

In the foregoing specification, the invention has been described withreference to specific embodiments thereof. It will, however, be evidentthat various modifications may be made thereto without departing fromthe broader spirit and scope of the invention. The specification anddrawings are, accordingly, to be regarded in an illustrative rather thana restrictive sense. The present invention is intended to be limited,therefore, only by the claims presented below.

What is claimed is:
 1. A desktop publishing system, comprising:a) anoutput display device, said output display device displaying:1) apalette window comprising a user defined objects panel and a predefinedobjects panel, the user defined panel comprising a list of user definedobjects and the predefined objects panel comprising a list of predinedobjects, and 2) a view window displaying an page comprising at least oneobject selected from one of said list of user defined objects and saidlist of predined objects; b) an input device, said input deviceselecting said object from one of said list of user defined objects andsaid list of predefined objects for display in said page at said viewwindow.
 2. The desktop publishing system of claim 1, wherein said inputdevice is a mouse.
 3. The desktop publishing system of claim 1, whereinsaid input device is a keyboard.
 4. The desktop publishing system ofclaim 1, wherein said output display device further displays an objecteditor window, said object editor window displaying a list of propertiesassociated with said object selected from one of said list of userdefined objects and said list of predefined objects.
 5. In a desktoppublishing system, a computer mediated method of generating anddisplaying a collection of objects representing a document,comprising:a) displaying a list of objects in a palette window on adisplay device, comprising:i) displaying a list of user defined objectsin a user defined objects panel in said palette window; ii) displaying alist of predefined objects in a predefined objects panel in said palettewindow; b) receiving input from an input device selecting an object fromone of said list of user defined objects and said list of predefinedobjects for said collection of objects; c) displaying said collection ofobjects in a page displayed in a view window of said display device,including said selected object.
 6. The method of claim 5, whereinreceiving input from an input device selecting an object from one ofsaid list of user defined objects and said list of predefined objectsfor said collection of objects further comprisesa mouse clicking on saidobject in said one of said list of user defined objects and said list ofpredefined.
 7. The method of claim 5, further comprising:a) receivinginput via said input device, said input selecting said object formodifying a property associated with said object; b) displaying in anobject editor window in said display device a value of said propertyassociated with said object; c) receiving at said input device inputmodifying said value of said property associated with said object. 8.The method of claim 7, wherein receiving input via said input device,said input selecting said object for modifying a property associatedwith said object includes receiving input via said input device, saidinput selecting said object from one of said list of user definedobjects and said list of predefined objects in said palette window. 9.The method of claim 8 further comprising:a) receiving input selectingone of said objects from said lists of user defined objects and saidpredefined objects, said selected object having a property associatedwith said selected object, said property having a value identical tosaid modified value of said property associated with said selectedobject; b) displaying said selected object in said user defined objectspanel in said palette window.
 10. The method of claim 7, whereinreceiving input via said input device, said input selecting said objectfor modifying a property associated with said object includes receivinginput via said input device, said input selecting said object from saidcollection of objects in said page displayed in said view window of saiddisplay device.
 11. The method of claim 10, wherein receiving at saidinput device input modifying said value of said property associated withsaid object further comprises displaying said object in said collectionof objects in said page displayed in said view window of said displaydevice.
 12. The method of claim 6, wherein displaying said collection ofobjects in a page in a view window of said display device, includingsaid selected object, comprises said mouse dragging said object fromsaid one of said list of user defined objects and said list ofpredefined objects and dropping said object in said collection ofobjects in said page of said view window of said display device.